home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Net Connect
/
NetConnect - Version 1.iso
/
amitcp
/
read me first
< prev
next >
Wrap
Text File
|
1997-03-05
|
13KB
|
348 lines
AmiTCP/IP DialUp 4.5 "Read Me First" File
=========================================
This file contains notes on changes that didn't make to other documentation.
Please read this through if you encounter any problems configuring AmiTCP/IP
DialUp 4.5.
Contents:
1. Summary of new features and improvements
2. Upgrading from earlier versions
3. Changes in the AmiTCP/IP setup
3.1 User information
3.2 IP provider setup
3.3 Serial line setup
3.4 Modem setup
4. Notes on supported Sana2 device drivers
5. Miscellaneous
5.1 db/User-Stopnet
5.2 ifconfig changes
5.3 Configuring without Domain Name Service
1. Summary of The New Features and Improvements
===============================================
This is the AmiTCP/IP DialUp Release 4.5 released 28-Jul-96. This release
contains new features, minor bug fixes and performance improvements over
previous versions.
Fixed bugs in 4.5:
* BOOTP now works (again)
* Configuration difficulties caused by small buffer sizes fixed
* Maximum MTU raised to 1524 (was 1500).
New features in 4.3:
* Improved and simplified configuration with IP provider profiles
* Direct Dial-Up support with BootPConfig
* New improved SLIP device (aslip.device)
* New API interface with Intelligent Priority Boosting
* Improved Napsaterm Telnet/Rlogin tool, added WB-icons
* Improved command line utilities (bootpconfig, ifconfig)
* Improved Arexx interface
* Default values shown in db/AmiTCP.config
* socket.library for AS225 compatibility
Fixed bugs in 4.3:
* AmiTCP/IP license key file and AmiTCP/IP itself can now be stored in any
file system
2. Upgrading from Earlier Versions
==================================
The `Install AmiTCP' on the installation disk supports upgrading from
earlier AmiTCP/IP versions. To make use of the new features generally
requires your to reconfigure AmiTCP/IP, though.
Although `Install AmiTCP' can copy existing AmiTCP/IP configuration files,
there might be other files (configuration files, program files) that you
have installed on top of the earlier AmiTCP/IP. These files are NOT copied
over automatically, and you must either copy the files manually, or
reinstall the software in question.
3. Changes in The AmiTCP/IP Setup
=================================
The way the configuration information is stored has been changed. The main
motivation has been to allow `Config AmiTCP' to recognize existing setup,
and provide proper default values to allow configuration changes without
requiring to re-enter *any* value, that does not need to be changed.
Also, the configuration information is divided into several independent
categories:
1) User information
2) IP provider setup
3) Serial line setup
4) Modem setup
These are handled in following subsections.
3.1 User Information
--------------------
The default user name is stored in ENVARC:LOGNAME and ENV:LOGNAME. LOGNAME
variable is also set up by the login command, which means that when startnet
is run, the user will not be changed. However, the configured default user
is restored when the ENV: is initialized from ENVARC: during a reboot.
The `login' command has been changed so that with usage "Login -f" it reads
the user name to login from ENV:LOGNAME.
The password setting during configuration has been made optional. Other user
information (real name, home directory etc.) is asked as before.
3.2 IP Provider Setup
---------------------
This release introduces "Provider profiles". These files collect all IP
provider specific information into one place. In other words, switching
providers just means replacing the existing profile with a new one!
This release contains few ready made profiles, but you should ask your
provider whether they already have a profile for the AmiTCP/IP. If they do,
fine, that's all you need. But if they do not, then you need to create one.
The information needed to make the profile is not dependent on the computer
platform, and exact instructions for some other platform will be of great
help in making the profile for the AmiTCP/IP.
If you provide the information from your provider, we can help you to
complete the script (via email to AmiTCP-Support@nsdi.fi). We also intend
to make the scripts available via our WWW service <http://www.nsdi.fi/>.
Profiles are stored in directory `AmiTCP:Providers'. The currently used
profile is stored in `AmiTCP:db/Provider.conf'. The profiles in
`AmiTCP:Providers' include:
FIN_Kolumbus - Kolumbus Internet Finland (static SLIP)
FIN_PersonalEunet - Eunet Finland (PPP)
FIN_TeleInetOpen - Telecom Finland InetOpen (SLIP, BOOTP)
GER_T-Online - German T-Online (dynamic SLIP)
Other - Template for DialUp IP providers
If the profile does not set the name server information, then they are
stored into `db/resolv.conf' by the `Config AmiTCP'. This file will be
overwritten by some provider profiles (see NSDynamic below).
The provider profile contains two parts. The first part starts from the
first line with "/*", and ends with the line starting with "*/". This part
contains configuration information, which `Config AmiTCP' interprets and
modifies. Bootpconfig also uses this information when configuring
AmiTCP/IP.
Fields in this section are:
Name Name for this profile
DialUp 1 if modem is needed. This is how `Config AmiTCP'
knows to ask modem configuration.
Interface Network interface name to be configured
InterfaceConfig Provider specific Sana2 options. Appended to serial
configuration from db/autointerfaces to form a
Sana2 device configuration file.
Only provider specific options should be set here.
NeedSerial 1 if a serial line is needed. This is how
'Config AmiTCP' knows to ask serial line related
options.
IPDynamic 1 if IP address is dynamic, 0 otherwise
IPAddr IP-address if static, leave blank if not known.
'Config AmiTCP' will ask this if necessary.
Bootpconfig can ask this at startup time also.
DestIP Destination IP address. This is NOT needed for
dialup configurations.
Gateway Default Gateway address. This is NOT needed for
dialup configurations.
Netmask Netmask of the interface. This is NOT needed for
dialup configurations.
NSDynamic 1 if name server configuration is dynamic. In this
case the dial script should set the name server
addresses ("Set NS1 x.x.x.x"). 0 otherwise.
Bootpconfig will create db/resolv.conf and
db/netdb-myhost (for compatibility with old email
programs) at startup time if name server configuration
is dynamic.
UseBootP 1 if BOOTP protocol should be used to configure
dynamic IP address, 0 otherwise. Your IP provider
must support BOOTP for you to be able to use it.
MTU Maximum transmit unit (in bytes) to use. The maximum
receive unit size is set in Sana2 configuration and
is set to maximum by `Config AmiTCP'.
0 represents the default maximum value, which should
be used on all LAN configurations.
Phone Provider phone number(s). Dial script command "Dial"
(in AmiTCP:ssrx/Dial.ssrx) will get this through
bootpconfig. It is in this section for
'Config AmiTCP' to be able to configure it.
Multiple phone numbers are separated with spaces.
The rest of the file is used as a dial-up script. As you see, the script
language is ARexx. Scripts can contain AmiTCP/IP scripting commands in
addition to normal ARexx commands. The command set is documented in
help/AmiTCP.guide.
If you use the "Other" profile, then a default manual login script is
appended to your profile. You can use this script to test the login
procedure, and then automate it when you need what kind of conversation is
needed with the IP provider service.
An example provider profile:
---8<---8<---8<---8<--->8--->8--->8--->8---
/* Provider Configuration Follows:
Name Other ; Name for this configuration
DialUp 1 ; This configuration needs a modem
Interface slip ; Interface name
InterfaceConfig "" ; Provider specific Sana2 options
NeedSerial 1 ; This configuration needs a serial line
IPDynamic 0 ; 1 = YES, 0 = NO
IPAddr ; IP-address if static
NSDynamic 0 ; 1 = YES, 0 = NO
UseBootP 0 ; 1 = YES, 0 = NO
MTU 576 ; Provider specific
Phone ; Provider phone number (without spaces)
*/
/* The rest is the Dialer script for this provider */
options results
signal on error
Say "Entering Manual Console Mode."
Status "Please log in"
ManualConsole
exit 0; /* Successful exit */
error:
Say "Command on line" SIGL "returned" RC ":" SerScript.LASTERROR
Exit 10
---8<---8<---8<---8<--->8--->8--->8--->8---
3.3 Serial Line Setup
---------------------
The serial line configuration is stored in db/autointerfaces. You
should not manually modify the db/autointerfaces file, but use the
'Config AmiTCP' to manage it.
The `Shared mode' is offered as the default. If Shared mode is used, the
dialup can be done without setting the modem to the ignore DTR mode (AT&D0).
This allows the modem connection to be dropped automatically when AmiTCP/IP
is terminated.
The EOF-mode setting is automated by both aslip.device and the newest
version of the ppp.device. These devices use the EOF-mode on only on devices
known to support it. You can enforce EOF-mode on or off by giving an
additional serial option, EOFMode or NoEOFMode, respectively, when `Config
AmiTCP' asks for additional serial options.
EOF mode is a technical detail in serial device usage that affects the CPU
usage of the serial traffic. EOF mode should be used if possible, but
unfortunately some add-on serial boards and replacement serial drivers do
not implement it. If you are using the normal AmigaOS serial.device with the
internal serial port, then you do NOT need to bother about the EOF-mode at
all.
The MTU value stored in db/autointerfaces is used as `MRU', i.e. `Maximum
Receive Unit', the maximum size allowed for an incoming packet. This is
always kept at maximum by the `Config AmiTCP', and should NOT be modified.
This version of AmiTCP/IP allows MTU (Maximum Transmit Unit, the maximum
size of sent packets) to be set independently. This value is asked in `IP
provider options' and is stored in the IP provider profile. This value can
also be changed and viewed at the run time with `ifconfig' utility.
The DoOffline option included into SLIP and PPP configuration in the
file `db/autointerfaces' instructs AmiTCP/IP to put the Sana2 device
offline when AmiTCP/IP is stopped. Putting SLIP or PPP device offline
will cause the modem connection to be dropped, if DTR is not ignored
by th modem (AT&D0 is not configured in modem init string).
3.4 Modem Setup
---------------
'Config AmiTCP' now also asks for the modem configuration. This includes
modem initialization string, and the dialing prefix. These are stored in
ENV:ModemInitString and ENV:ModemDialPrefix, respectively (also in ENVARC:).
The modem initialization string is dependent of the modem you have. If you
are using a terminal program, you probably have a modem initialization
sting configured for it. This can be used as is with AmiTCP/IP as well.
Generally the modem initialization string should contain the following:
1) The command introducer "AT" (for Hayes compatible modems)
2) Reset to factory defaults: "&F"
3) Sense carrier: "&C1"
4) Disconnect on DTR drop: "&D2"
5) Hardware handshake: "&R1" (7Wire mode, need 7 wire cable)
You need to confirm the actual values from the manual of your modem. The
scripts using the ModemInitString assume it to return OK, so at least the
command introducer must be given.
The modem dial prefix is usually "ATDT" (touch tone dial).
4. Notes on Supported Sana2 Device Drivers
==========================================
AmiTCP/IP DialUp supports only following Sana-II drivers:
SLIP: aslip.device is a new slip Sana2 device with slightly modified
configuration file interface. `Config AmiTCP' requires it if
SLIP protocol is used.
PPP: ppp.device version 1.45 or later is needed for PPP. Evaluation
version is available from AmiNet (for example wuarchive.wustl.edu),
file /pub/aminet/comm/net/PPP1_45.lha.
5. Miscellaneous
================
5.1 `db/User-Stopnet'
---------------------
The `stopnet' script has been modified to execute `db/User-Stopnet', if it
exists and AmiTCP/IP is running.
5.2 `ifconfig' Changes
----------------------
Ifconfig now supports new usage, `ifconfig' without any arguments. It shows
the currently configured interface.
Ifconfig also gives textual presentations to all interface flags that are
set. It also reports the set MTU, hardware type and hardware address, if
applicable. The MTU can also be set, for example:
ifconfig slip mtu 296
will set the MTU of the interface `slip' to 296 (`slip' is assumed to be
configured already).
5.3 Configuring AmiTCP/IP without Domain Name Service
-----------------------------------------------------
If you run AmiTCP/IP without a connection to the Internet, the Domain Name
Service might not be available. AmiTCP/IP configuration expects that it can
find out the host name from the IP address of your Amiga. If the domain
name service is not available, you should add a suitable IP-address-to-
host-name mapping to the `AmiTCP:db/hosts' file. See the existing `hosts'
file for the format of the file.
EOF